Programmed dispensing of consumable compositions

ABSTRACT

Methods and systems for administering consumable compositions according to a programmed dosing schedule are provided. A method for administering a consumable composition may comprise one or more of the following steps: (a) dispensing a first dose of a consumable composition according to a programmed dosing schedule; and (b) detecting at least one ingestion of the consumable composition. A method for administering a consumable composition may comprise one or more of the following steps: (a) dispensing a first dose of a consumable composition according to a programmed dosing schedule; (b) detecting at least one aspect of the consumable composition; and (c) providing a user notification according to the aspect of the consumable composition. A system for administering a consumable composition may comprise: (a) means for dispensing a first dose of a consumable composition according to a programmed dosing schedule; and (b) means for detecting at least one ingestion of the consumable composition. A system for administering a consumable composition may carry out one or more of the following steps: (a) means for dispensing a first dose of a consumable composition according to a programmed dosing schedule; (b) means for detecting at least one aspect of the consumable composition; and (c) means for providing a user notification according to the aspect of the consumable composition.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is related to and claims the benefit of theearliest available effective filing date(s) from the following listedapplication(s) (the “Related Applications”) (e.g., claims earliestavailable priority dates for other than provisional patent applicationsor claims benefits under 35 USC §119(e) for provisional patentapplications, for any and all parent, grandparent, great-grandparent,etc. applications of the Related Application(s)).

RELATED APPLICATIONS

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of United States patentapplication having United States Postal Service Express Mailing LabelNo. EM117518327US, entitled Programmed Dispensing of ConsumableCompositions, naming Eric C. Leuthardt, Clarence T. Tegreene, Lowell L.Wood, Jr., Roderick A. Hyde and Robert W. Lord as inventors, filed Nov.29, 2007, which is currently co-pending, or is an application of which acurrently co-pending application is entitled to the benefit of thefiling date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of United States patentapplication having United States Postal Service Express Mailing LabelNo. EM117519305, entitled Programmed Dispensing of ConsumableCompositions, naming Roderick A. Hyde, Eric C. Leuthardt, Robert W.Lord, Clarence T. Tegreene and Lowell L. Wood, Jr. as inventors, filedDec. 7, 2007, which is currently co-pending, or is an application ofwhich a currently co-pending application is entitled to the benefit ofthe filing date.

The United States Patent Office (USPTO) has published a notice to theeffect that the USPTO's computer programs require that patent applicantsreference both a serial number and indicate whether an application is acontinuation or continuation-in-part. Stephen G. Kunin, Benefit ofPrior-Filed Application, USPTO Official Gazette Mar. 18, 2003, availableat http://www.uspto.gov/web/offices/com/sol/og/2003/week11/patbene.htm.The present Applicant Entity (hereinafter “Applicant”) has providedabove a specific reference to the application(s) from which priority isbeing claimed as recited by statute. Applicant understands that thestatute is unambiguous in its specific reference language and does notrequire either a serial number or any characterization, such as“continuation” or “continuation-in-part,” for claiming priority to U.S.patent applications. Notwithstanding the foregoing, Applicantunderstands that the USPTO's computer programs have certain data entryrequirements, and hence Applicant is designating the present applicationas a continuation-in-part of its parent applications as set forth above,but expressly points out that such designations are not to be construedin any way as any type of commentary and/or admission as to whether ornot the present application contains any new matter in addition to thematter of its parent application(s).

All subject matter of the Related Applications and of any and allparent, grandparent, great-grandparent, etc. applications of the RelatedApplications is incorporated herein by reference to the extent suchsubject matter is not inconsistent herewith.

BACKGROUND

Programmed regimens of consumable compositions may be prescribed by aphysician or may simply be desirable for the health and well-being of anindividual. However, confusion may arise concerning the schedule,dosage, and/or compliance with a programmed dosing regimen.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 shows a high-level block diagram of a beverage container.

FIG. 2 is a high-level logic flowchart of a process.

FIG. 3 is a high-level logic flowchart of a process depicting alternateimplementations of FIG. 2.

FIG. 4 is a high-level logic flowchart of a process depicting alternateimplementations of FIG. 2.

FIG. 5 is a high-level logic flowchart of a process depicting alternateimplementations of FIG. 2.

FIG. 6 is a high-level logic flowchart of a process depicting alternateimplementations of FIG. 2.

FIG. 7 is a high-level logic flowchart of a process.

FIG. 8 is a high-level logic flowchart of a process depicting alternateimplementations of FIG. 7.

FIG. 9 is a high-level logic flowchart of a process depicting alternateimplementations of FIG. 7.

FIG. 10 is a high-level logic flowchart of a process depicting alternateimplementations of FIG. 7.

FIG. 11 is a high-level logic flowchart of a process depicting alternateimplementations of FIG. 7.

FIG. 12 is a high-level logic flowchart of a process depicting alternateimplementations of FIG. 7.

FIG. 13 is a high-level logic flowchart of a process depicting alternateimplementations of FIG. 7.

FIG. 14 is a high-level logic flowchart of a process depicting alternateimplementations of FIG. 7.

DETAILED DESCRIPTION

In the following detailed description, reference is made to theaccompanying drawings, which form a part hereof. In the drawings,similar symbols typically identify similar components, unless contextdictates otherwise. The illustrative embodiments described in thedetailed description, drawings, and claims are not meant to be limiting.Other embodiments may be utilized, and other changes may be made,without departing from the spirit or scope of the subject matterpresented here.

FIG. 1 illustrates an example environment in which one or moretechnologies may be implemented. A consumable composition dispensingsystem 100 may comprise a beverage container 110 to be used by user 190.The beverage container 110 may include any receptacle configured forretaining a liquid or gel composition. For example, the beveragecontainer 110 may include a cup, glass, mug, bowl, pitcher, jug, and thelike.

The beverage container 110 may include a processor 120, a communicationsmodule 130, a user interface 140, a sensor module 150, an integratedconsumable composition dispenser module 160, and/or an integratedsterilization module 187.

Processor 120 may include communications logic 122, user interface logic123, sensing logic 124, dispensing logic 125, memory 126, and/orsterilization logic 188.

Memory 126 may include user identification data 126-1 and/or consumablecomposition dispensing programs 126-2.

User interface 140 may include a notification module 142, anidentification module 144, and/or a user input module 146.

Sensor module 150 may include one or more of a light source sensor, aposition sensor, an emission sensor, a spectrophotometer, an infrared orultraviolet sensor, a biometric sensor and the like.

The consumable composition dispensing system 100 may further include anexternal consumable composition dispenser 170 and/or externalsterilization module 186.

FIG. 2 illustrates an operational flow 200 representing exampleoperations related to programmed dispensing of consumable compositions.In FIG. 2 and in following figures that include various examples ofoperational flows, discussion and explanation may be provided withrespect to the above-described examples of FIG. 1, and/or with respectto other examples and contexts. However, it should be understood thatthe operational flows may be executed in a number of other environmentsand contexts, and/or in modified versions of FIG. 1. Also, although thevarious operational flows are presented in the sequence(s) illustrated,it should be understood that the various operations may be performed inother orders than those which are illustrated, or may be performedconcurrently.

After a start operation, the operational flow 200 moves to a dispensingoperation 210, where dispensing a first dose of a consumable compositionaccording to a programmed dosing schedule may occur (e.g. distributing apharmaceutical composition in accordance with a user orphysician-defined regimen). For example, as shown in FIG. 1, integratedconsumable composition dispenser module 160, and or external consumablecomposition dispenser module 170 may distribute doses (e.g. 30 mg) of aconsumable composition (e.g. an anti-depressant, such as Paroxotene)into a beverage container 110 (e.g. a cup).

The consumable composition may be a pharmaceutical compositionincluding, but not limited to, one or more of the following: 5-alphareductase inhibitors, 5-HT antagonists, ACE inhibitors, adrenergicagonists, adrenergic neurone blockers, alkalising agent, alpha blockers,aminoglycosides, anaesthetics, analgesics, androgens, angiotensinreceptor blockers, antiallergics, antiandrogens, antianginals,antiarrhythmics, antibiotics, anticholinergics, anticholinesterase,anticoagulants, anticonvulsants, antidepressants, antidiarrhoeals,antidopaminergics, anti-emetics, antiepileptics, antiflatulents,antifungal, antifungals, anti-hemophilics, antihistamine,antihistamines, antiplatelets, antipsychotics, antiseptics,antispasmodic, antispasmodics, antithyroid drugs, antitussives,anxiolytics, astringents, barbiturates, benzodiazepine, beta-receptorantagonists, beta-receptor blocker, bile acid sequestrants,bronchodilators, calcitonins, calcium channel blockers, cannabinoids,carbonic anhydrase inhibitors/hyperosmotics, cardiac glycosides,cerumenolyti, cholinergics, corticosteroids, COX-2 selective inhibitors,cycloplegics, cyclopyrrolone, cytoprotectants, decongestants,diphosphonates, diuretics, dopamine antagonist, emetic, fibrinolytics,fluoroquinolones, gonadotropins, growth hormones, H2-receptorantagonists, haemostatic drugs, heparins, hormonal contraceptives,hypnotics, hypolipidaemic agents, imidazoles, immunoglobulins,immunosuppressants, insulin, interferons, laxatives, local anesthetics,mast cell inhibitors, miotics, monoclonal antibodies, movement disorderdrugs, mucolytics, muscle relaxants, mydriatics, neuromuscular drugs,nitrates, nitroglycerin, NSAIDs, ocular lubricants, opioids,parasympatholytics, parasympathomimetics, peripheral activators,polyenes, prostaglandin agonists/prostaglandin inhibitors, prostaglandinanalogues, proton pump inhibitors, quinolones, reflux suppressants,selective alpha-1 blocker, sildenafil, statins, steroids, stimulants,sulfa drugs, sympathomimetics, thyroid hormones, topical anesthetics,topical antibiotics, vaccines, vasoconstrictors, vasodilators,vasopressin analogues, and the like.

The consumable composition may be a neutraceutical compositionincluding, but not limited to, one or more of the following: vitamins(e.g., ascorbic acid, pyridoxine, riboflavin), minerals (e.g., calciumsalts, zinc salts, potassium salts), hormones (e.g., cortisone,pancreatin, epinephrine), biochemicals (e.g., adenosine triphosphate,coenzyme A, cysteine), glandulars (e.g., thyroid, pancreas, adrenalcortex), herbals (e.g., ginkgo, garlic, goldenseal, echinacea), and thelike.

At the operation 302, detecting at least one ingestion of the consumablecomposition may occur (e.g. a user has complied with a programmed dosingschedule for the consumable composition by swallowing the consumablecomposition). For example, as shown in FIG. 1, the sensing logic 124 maybe operably coupled to sensor module 150. Upon ingestion of a consumablecomposition, the sensor module 150 may provide a signal to sensing logic124 that ingestion has occurred.

FIG. 3 illustrates alternative embodiments of the example operationalflow 200 of FIG. 2. FIG. 3 illustrates example embodiments where thedetecting operation 302 may include at least one additional operation.Additional operations may include an operation 304, and/or an operation306.

Further, at the operation 304, detecting a presence of a bodily fluid(e.g. biometric detection) may occur. For example, as shown in FIG. 1,the sensor module 150 may include a biometric sensor which senses thepresence of saliva, perspiration, sebum and the like, either on thesurface of the beverage container 110 or as a component of the contentstherein.

At the operation 306, detecting a movement of a beverage containercontaining the consumable composition (e.g. accelerometric detection ofa user-initiated movement) may occur. For example, as shown in FIG. 1,the sensor module 150 may include an accelerometer, inertial motionsensor and the like, which may sense the movement of the beveragecontainer 110.

FIG. 4 illustrates alternative embodiments of the example operationalflow 200 of FIG. 2. FIG. 4 illustrates example embodiments where thedetecting operation 302 may include at least one additional operation.Additional operations may include an operation 402, an operation 404, anoperation 406, and/or an operation 408.

At the operation 402, detecting a pressure applied to a beveragecontainer containing the consumable composition (e.g. fiber opticpressure detection of a user grasping the beverage container) may occur.For example, as shown in FIG. 1, the sensor module 150 may include afiber optic pressure sensor, mechanical deflection pressure sensor,strain gauge pressure sensor, piezoresistive pressure sensor,microelectromechanical (MEMS) pressure sensor, variable capacitancepressure sensor, and the like which senses a pressure applied to thebeverage container 110.

Similarly, at the operation 404, detecting a volume of fluid in abeverage container containing the consumable composition may occur (e.g.optical detection). For example, as shown in FIG. 1, the sensor modulemay include an optical or mechanical sensor which may sense a volume ofthe fluid in the beverage container 110.

At the operation 406, detecting a mass of fluid in a beverage containercontaining the consumable composition may occur (e.g. mechanicaldeflection pressure detection). For example, as shown in FIG. 1, thesensor module 150 may include a fiber optic pressure sensor, mechanicaldeflection pressure sensor, strain gauge pressure sensor, piezoresistivepressure sensor, microelectromechanical (MEMS) pressure sensor, variablecapacitance pressure sensor, and the like which senses a mass of fluidcontained in the beverage container 110.

At the operation 408, detecting a capacitance of fluid in a beveragecontainer containing the consumable composition may occur (e.g. chemicalfield effect transistor detection). For example, as shown in FIG. 1, thesensor module 150 may include a capacitive concentration sensor whichmay sense a concentration of the consumable composition present in thebeverage container 110.

FIG. 5 illustrates alternative embodiments of the example operationalflow 200 of FIG. 2. FIG. 5 illustrates example embodiments where thedetecting operation 302 may include at least one additional operation.Additional operations may include an operation 502, an operation 504, anoperation 506, an operation 508, and/or an operation 510.

At the operation 502, detecting an outflow rate of the consumablecomposition from a beverage container containing the consumablecomposition may occur (e.g. a rate at which a physical, chemical,electrical, or optical property changes). For example, as shown in FIG.1, the sensor module 150 may include a fiber optic pressure/outflowsensor, mechanical deflection pressure/outflow sensor, strain gaugepressure/outflow sensor, piezoresistive pressure/outflow sensor,microelectromechanical (MEMS) pressure/outflow sensor, variablecapacitance pressure/outflow sensor, flowmeters, and the like whichsense an outflow from the beverage container 110 containing theconsumable composition. Such an outflow may indicate a proper ingestionor an improper disposal of the consumable composition, depending on theoutflow rate. For example, proper ingestion might be indicated by anoutflow rate indicative of normal drinking, while improper disposalmight be indicated by an outflow rate indicative of dumping the contentsof the cup by upending the cup.

Further, at the operation 504, detecting a rate of change of a volume ofa fluid in a beverage container containing the consumable compositionmay occur (e.g. a magnetic flowmeter measuring volume outflow from thebeverage container over time). Further, at the operation 506, detectinga rate of change of a mass of a fluid in a beverage container containingthe consumable composition may occur (e.g. a piezoresistive pressuresensor measuring the change in the mass present in a beverage containerover time). Further, at the operation 508, detecting a rate of change ofa capacitance of a fluid in a beverage container containing theconsumable composition may occur (e.g. a capacitive sensor measuring thechange of capacitance of the fluid in the beverage container over time).

At the operation 510, detecting a degree of inclination of a beveragecontainer containing the consumable composition may occur (e.g. amechanism may detect that a user is rotating the beverage container by acertain degree relative to its designed resting position so as to ingestits contents). For example, as shown in FIG. 1, the sensor module 150may include an inclinometer and the like. The degree of incline of thebeverage container 110 may indicate a proper ingestion or an improperdisposal of the consumable composition, depending on the degree ofincline.

FIG. 6 illustrates alternative embodiments of the example operationalflow 200 of FIG. 2. FIG. 6 illustrates example embodiments where theoperational flow 200 may include at least one additional operation.Additional operations may include a delaying operation 602.

At the operation 602, delaying a dispensing of a second dose of theconsumable composition according to the detecting the at least oneingestion of the consumable composition may occur (e.g. a mechanismdelaying dispensing until the first dose will have been metabolized).For example, as shown in FIG. 1, the sensing logic 124 may provide datafrom the sensor module 150 regarding an amount of consumable compositioningested to the detecting logic 121. The dispensing logic 125 may delaya dispensation of a second dose of the consumable composition by theintegrated consumable composition dispenser module 160, and/or theexternal consumable composition dispenser module 170 until the detectinglogic 121 indicates of an ingestion of a previously dispensed dose ofthe consumable composition.

FIG. 7 illustrates an operational flow 700 representing exampleoperations related to dispensing a consumable composition. FIG. 7illustrates an example embodiment.

At the detecting operation 220, detecting at least one aspect of theconsumable composition (e.g. capacitive concentration detection) mayoccur. For example, as shown in FIG. 1, an aspect of the consumablecomposition may be detected by measuring a physical, chemical, optical,and/or electrical property with sensor module 150 operably coupled tosensing logic 124.

Further, an aspect of the consumable composition may be detected byreceiving communications data from a communications module operablycoupled to communications logic 122. An aspect of the consumablecomposition may be detected by accepting a user input by a userinterface 140 operably coupled to user interface logic 123. An aspect ofthe consumable composition may be detected by receiving dispensing datafrom an integrated consumable composition dispenser module 160 and/or anexternal consumable composition dispenser module 170 operably coupled todispensing logic 125. An aspect of the consumable composition may bedetected by receiving sterilization data from an integratedsterilization module 186 and or an external sterilization module 187operably coupled to sterilization logic 188.

The aspect of the consumable composition may include, but is not limitedto, an amount of consumable composition dispensed into the beveragecontainer 110, an amount of consumable composition present in thebeverage container 110, an amount of the composition removed from thebeverage container 110, an identity of the consumable composition, anidentity of a user 190, a user input, a programmed schedule fordispensing the consumable composition, and the like.

The aspect of the consumable composition may be communicated via thecommunication module 130 to an outside entity. The outside entity may bea monitoring system 180 or a controllable device 185 which may becontrolled according to the aspect of the consumable composition.

Monitoring system 180 may also transmit a notification (e.g. anotification that a programmed dosing schedule has been transmitted tothe system 100) to a communications device 181 (e.g. a cell phone,satellite phone, Blackberry®, and/or land-line phone), e-mail system 182(e.g. an IMAP, POP3, SMTP, and/or HTTP e-mail server having an e-mailaccount associated with a user 190), text messaging system 183 (e.g. SMSsystem in GSM) and/or a computing device 184 (e.g. a personal digitalassistant (PDA), personal computer, laptop, music player and/or gamingdevice).

After a start operation, a dispensing operation 210, and a detectingoperation 220, the operational flow 700 moves to a user notificationoperation 710, where providing a user notification according to theaspect of the consumable composition may occur (e.g. a notification of adispensed dose of a consumable composition according to an amount of theconsumable composition dispensed). For example, as shown in FIG. 1, theuser interface logic 123 may cause the notification module 142 of theuser interface 140 to provide a notification that an amount ofconsumable composition is about to be dispensed. The notification mayinclude the identity of the consumable composition (e.g., a trade nameand/or chemical composition of the consumable composition) and thetiming of the dispensation (e.g. “20 minutes ago”).

FIG. 7 further illustrates alternative embodiments of the exampleoperational flow 700 of FIG. 7. FIG. 7 illustrates example embodimentswhere the notification operation 710 may include at least one additionaloperation. Additional operations may include an operation 712.

At the operation 712, providing a notification of an upcoming dose mayoccur (e.g. a dose scheduled according to a programmed dosing schedulewill be dispensed at a given time). For example, as shown in FIG. 1, theuser interface logic 140 may cause the notification module 142 of theuser interface 140 to provide a notification to the user 190.

FIG. 7 further illustrates example embodiments where the upcoming dosenotification operation 712 may include at least one additionaloperation. Additional operations may include an operation 714, anoperation 716, and/or an operation 718.

At the operation 714, providing a visual notification may occur (e.g. agraphical notice on a display screen). For example, as shown in FIG. 1,the notification module 142 of the user interface 140 may include aflashing LED, LCD display screen, and the like.

At the operation 716, vibrating a beverage container may occur (e.g.movement of an asymmetrical mass). For example, as shown in FIG. 1, thenotification module 142 may include an asymmetrical rotating massoperably coupled to a motor. Upon application of power to the motor, themass may be rotated such that it induces vibration in the beveragecontainer 110.

At the operation 718, providing an audible notification may occur (e.g.a simple beep or voice command). For example, as shown in FIG. 1, thenotification module 142 of the user interface 140 may include a speakerassembly, and the like.

FIG. 8 illustrates alternative embodiments of the example operationalflow 700 of FIG. 7. FIG. 8 illustrates example embodiments where theupcoming dose notification operation 712 may include at least oneadditional operation. Additional operations may include an operation802, an operation 804, an operation 806, and/or an operation 808.

At the operation 802, transmitting a notification to a communicationsdevice may occur (e.g. placing an automated call to a user's homephone). For example, as shown in FIG. 1, the communications module 130may transmit a notification to a monitoring system 180 linked to acommunications device 181. The communications device 181 may include acell phone, satellite phone, Blackberry®, land-line phone, and the like.

At the operation 804, transmitting a notification to an e-mail systemmay occur (e.g. an automated e-mail notice to a user's e-mail account).For example, as shown in FIG. 1, the communications module 130 maytransmit a notification to a monitoring system 180 linked to an e-mailsystem 182 including an IMAP, POP3, SMTP, and/or HTTP e-mail serverhaving an e-mail account associated with a user 190.

At the operation 806, transmitting a notification to a text messagingsystem may occur (e.g. an automated text message to a user's cellphone). For example, as shown in FIG. 1, the communications module 130may transmit a notification to a monitoring system 180 linked to a textmessaging system 183, such as a SMS system in GSM.

At the operation 808, transmitting a notification to a computing devicemay occur (e.g. an automated instant message to a user's computer). Forexample, as shown in FIG. 1, the communications module 130 may transmita notification to a monitoring system 180 linked to a computing device184. The computing device 184 may include a personal digital assistant(PDA), personal computer, laptop, music player, gaming device, and thelike capable of receiving instant messages from IM providers such asMicrosoft®.

FIG. 9 illustrates alternative embodiments of example operational flow700 of FIG. 7. FIG. 9 illustrates an example embodiment where the usernotification operation 710 may include at least one additionaloperation. Additional operations may include an operation 910.

At operation 910, providing a notification of a dispensed dose may occur(e.g. a dose scheduled according to a programmed dosing schedule hasbeen dispensed at a given time). For example, as shown in FIG. 1, theuser interface logic 123 may cause the notification module 142 of theuser interface 140 to provide a notification that an amount of theconsumable composition has been dispensed. The notification may includethe identity of the consumable composition and the timing of thedispensation.

FIG. 9 further illustrates alternative embodiments of the exampleoperational flow 700 of FIG. 7. FIG. 9 illustrates example embodimentswhere the dispensed dose notification operation 910 may include at leastone additional operation. Additional operations may include an operation912, an operation 914, an operation 916, an operation 918, and/or anoperation 920.

At the operation 912, providing a visual notification may occur (e.g. animage of a beverage cup containing a consumable composition displayed onan LCOS display). For example, as shown in FIG. 1, the notificationmodule 142 of the user interface 140 may include a flashing LED, an LCDor LCOS display screen, and the like.

At the operation 914, vibrating a beverage container may occur (e.g.periodic movement of an oscillating mass). For example, as shown in FIG.1, the beverage container 110 may include an asymmetrical rotating massoperably coupled to a motor. Upon application of power to the motor, themass may be rotated such that it induces vibration in the beveragecontainer 110.

At the operation 916, providing an audible notification may occur (e.g.a vocal notification). For example, as shown in FIG. 1, the notificationmodule 142 of the user interface 140 may include a speaker assembly, andthe like, over which a notification may be transmitted. In someinstances, the notification includes the dose dispensed and the materialdispensed (e.g., “100 mg of Viagra was just dispensed into your cup”).

At the operation 918, dispensing a second consumable compositioncharacterized by an indicator color may occur (e.g. red, blue or green).For example, as shown in FIG. 1, the dispensing logic 125 may cause theintegrated consumable composition dispenser module 160 and/or theexternal consumable composition dispenser module 170 to dispense asecond consumable composition (e.g., Allura Red AC food coloring[2-naphthalenesulfonic acid]) which has a visible indicator color (e.g.,red) different from the consumable composition (e.g., a white analgesic,such as acetylsalicylic acid). Further, at the operation 920, dispensinga second consumable composition characterized by an indicator colorvisible under ultraviolet light may occur (e.g. tonic water comprisingquinine). Similarly, compositions visible under other electromagneticradiation wavelength ranges, such as infrared, may be used.

FIG. 10 illustrates alternative embodiments of the example operationalflow 700 of FIG. 9. FIG. 10 illustrates example embodiments where thedispensed dose notification operation 910 may include at least oneadditional operation. Additional operations may include an operation1002, an operation 1004, an operation 1006, and/or an operation 1008.

At the operation 1002, transmitting a notification to a communicationsdevice may occur (e.g., sending a text message to a user's cell phone).For example, as shown in FIG. 1, the communications module 130 maytransmit a notification to a monitoring system 180 linked to acommunications device 181. The communications device 181 may include acell phone, Blackberry®, land-line phone, and the like.

At the operation 1004, transmitting a notification to an e-mail systemmay occur (e.g. sending an e-mail to an IMAP, POP3, SMTP, and/or HTTPe-mail server having an e-mail account associated with a user 190). Forexample, as shown in FIG. 1, the communications module 130 may transmita notification to a monitoring system 180 linked to an e-mail system182.

At the operation 1006, transmitting a notification to a text messagingsystem may occur (e.g. sending text message to an SMS system in GSM).For example, as shown in FIG. 1, the communications module 130 maytransmit a notification to a monitoring system 180 linked to a textmessaging system 183.

At the operation 1008, transmitting a notification to a computing devicemay occur (e.g. sending an instant message to a personal computer). Forexample, as shown in FIG. 1, the communications module 130 may transmita notification to a monitoring system 180 linked to a computing device184. The computing device 184 may include a personal digital assistant(PDA), personal computer, laptop, music player, gaming device, and thelike.

FIG. 11 illustrates alternative embodiments of example operational flow700 of FIG. 7. FIG. 11 illustrates an example embodiment where the usernotification operation 710 may include at least one additionaloperation. Additional operations may include an operation 1110.

At operation 1110, providing a notification of a missed ingestion of adose may occur (e.g. a dose dispensed according to a programmed dosingschedule has not been ingested). For example, as shown in FIG. 1, theuser interface logic 123 may cause the notification module 142 of theuser interface 140 to provide a notification that ingestion of theconsumable composition has been missed. The notification may include theidentity of the consumable composition and the timing of thedispensation (e.g., a dose of Percoset was dispensed at 3:00 pm).

FIG. 11 further illustrates alternative embodiments of the exampleoperational flow 700 of FIG. 7. FIG. 11 illustrates example embodimentswhere the dispensed dose notification operation 1110 may include atleast one additional operation. Additional operations may include anoperation 1112, an operation 1114, an operation 1116, an operation 1118,and/or an operation 1120.

At the operation 1112, providing a visual notification may occur (e.g.an LED may change colors from green to red). For example, as shown inFIG. 1, the notification module 142 of the user interface 140 mayinclude a flashing LED, LCD display screen, and the like.

At the operation 1114, vibrating a beverage container may occur (e.g.rotation of an asymmetrical mass). For example, as shown in FIG. 1, thebeverage container 110 may include an asymmetrical rotating massoperably coupled to a motor. Upon application of power to the motor, themass may be rotated such that it induces vibration in the beveragecontainer 110.

At the operation 1116, providing an audible notification may occur (e.g.an audio broadcast of a ring tone). For example, as shown in FIG. 1, thenotification module 142 of the user interface 140 may include a speakerassembly, and the like.

At the operation 1118, dispensing a second consumable compositioncharacterized by an indicator color may occur. For example, as shown inFIG. 1, the dispensing logic 125 may cause the integrated consumablecomposition dispenser module 160 and/or the external consumablecomposition dispenser module 170 to dispense a second consumablecomposition (e.g., Sunset Yellow FCF food coloring [disodium salt of6-hydroxy-5-[(4-sulfophenyl)azo]-2-naphthalenesulfonic acid]) separatefrom the consumable composition (e.g., an antihistamine) which has avisible indicator color (e.g. yellow) different color than theconsumable composition (e.g. white). Further, at the operation 1120,dispensing a second consumable composition characterized by an indicatorcolor visible under ultraviolet light may occur (e.g. a solutioncontaining Vitamin B-12).

FIG. 12 illustrates alternative embodiments of the example operationalflow 700 of FIG. 11. FIG. 12 illustrates example embodiments where themissed dose ingestion notification operation 1110 may include at leastone additional operation. Additional operations may include an operation1202, an operation 1204, an operation 1206, and/or an operation 1208.

At the operation 1202, transmitting a notification to a communicationsdevice may occur (e.g. sending an instant message to a Blackberry®device). For example, as shown in FIG. 1, the communications module 130may transmit a notification to a monitoring system 180 linked to acommunications device 181. The communications device 181 may include acell phone, Blackberry®, land-line phone, and the like.

At the operation 1204, transmitting a notification to an e-mail systemmay occur (e.g. an e-mail to an IMAP, POP3, SMTP, and/or HTTP e-mailserver having an e-mail account associated with a user 190). Forexample, as shown in FIG. 1, the communications module 130 may transmita notification to a monitoring system 180 linked to an e-mail system182.

At the operation 1206, transmitting a notification to a text messagingsystem may occur (e.g. text message to an SMS system in GSM). Forexample, as shown in FIG. 1, the communications module 130 may transmita notification to a monitoring system 180 linked to a text messagingsystem 183.

At the operation 1208, transmitting a notification to a computing devicemay occur (e.g., an instant message via an online gaming system, such asthe Xbox Live® system marketed by the Microsoft® Corporation). Forexample, as shown in FIG. 1, the communications module 130 may transmita notification to a monitoring system 180 linked to a computing device184. The computing device 184 may include a personal digital assistant(PDA), personal computer, laptop, music player, gaming device, and thelike.

FIG. 13 illustrates alternative embodiments of example operational flow700 of FIG. 7. FIG. 13 illustrates an example embodiment where the usernotification operation 710 may include at least one additionaloperation. Additional operations may include an operation 1310.

At operation 1310, providing a notification of a failed dispensation ofa dose may occur (e.g. a dose scheduled to have been dispensed accordingto a programmed dosing schedule has not been dispensed). For example, asshown in FIG. 1, the user interface logic 123 may cause the notificationmodule 142 of the user interface 140 to provide a notification that anamount of the consumable composition has failed to dispense (e.g., anaudio notice stating “A dispensation of your Vicodin has failed.”) Thenotification may include the identity of the consumable composition andthe timing of the dispensation.

FIG. 13 further illustrates alternative embodiments of the exampleoperational flow 700 of FIG. 7. FIG. 13 illustrates example embodimentswhere the failed dispensation of a dose notification operation 1310 mayinclude at least one additional operation. Additional operations mayinclude an operation 1312, an operation 1314, an operation 1316, anoperation 1318, and/or an operation 1320.

At the operation 1312, providing a visual notification may occur (e.g. atextual display on an LCD display). For example, as shown in FIG. 1, thenotification module 142 of the user interface 140 may include a flashingLED, LCD display screen, and the like.

At the operation 1314, vibrating a beverage container may occur (e.g. aspring-loaded mass may be released). For example, as shown in FIG. 1,the beverage container 110 may include an asymmetrical rotating massoperably coupled to a motor. Upon application of power to the motor, themass may be rotated such that it induces vibration in the beveragecontainer 110.

At the operation 1316, providing an audible notification may occur (e.g.the mechanical ringing of a bell). For example, as shown in FIG. 1, thenotification module 142 of the user interface 140 may include a speakerassembly, and the like.

At the operation 1318, dispensing a second consumable compositioncharacterized by an indicator color may occur. For example, as shown inFIG. 1, the dispensing logic 125 may cause the integrated consumablecomposition dispenser module 160 and/or the external consumablecomposition dispenser module 170 to dispense a second consumablecomposition (e.g., Brilliant Blue FCF) separate from the consumablecomposition (e.g., riboflavin) which has a visible indicator color(e.g., blue) distinct from that of the consumable composition (e.g.yellow). Further, at the operation 1320, dispensing a second consumablecomposition characterized by an indicator color visible underultraviolet light may occur (e.g., chlorophyll extract).

FIG. 14 illustrates alternative embodiments of the example operationalflow 700 of FIG. 7. FIG. 14 illustrates example embodiments where thefailed dispensation of a dose notification operation 1310 may include atleast one additional operation. Additional operations may include anoperation 1402, an operation 1404, an operation 1406, and/or anoperation 1408.

At the operation 1402, transmitting a notification to a communicationsdevice may occur (e.g., an automated voicemail sent to a cell phoneand/or land line phone). For example, as shown in FIG. 1, thecommunications module 130 may transmit a notification to a monitoringsystem 180 linked to a communications device 181. The communicationsdevice 181 may include a cell phone, Blackberry®, land-line phone, andthe like.

At the operation 1404, transmitting a notification to an e-mail systemmay occur (e.g. an e-mail to an IMAP, POP3, SMTP, and/or HTTP e-mailserver having an e-mail account associated with a user 190). Forexample, as shown in FIG. 1, the communications module 130 may transmita notification to a monitoring system 180 linked to an e-mail system182.

At the operation 1406, transmitting a notification to a text messagingsystem may occur (e.g. text message to an SMS system in GSM). Forexample, as shown in FIG. 1, the communications module 130 may transmita notification to a monitoring system 180 linked to a text messagingsystem 183.

At the operation 1408, transmitting a notification to a computing devicemay occur (e.g., an instant message to a music player via a musicdownload service, such as the iTunes® service marketed by Apple® Inc.).For example, as shown in FIG. 1, the communications module 130 maytransmit a notification to a monitoring system 180 linked to a computingdevice 184. The computing device 184 may include a personal digitalassistant (PDA), personal computer, laptop, music player, gaming device,and the like.

Those having skill in the art will recognize that the state of the arthas progressed to the point where there is little distinction leftbetween hardware and software implementations of aspects of systems; theuse of hardware or software is generally (but not always, in that incertain contexts the choice between hardware and software can becomesignificant) a design choice representing cost vs. efficiency tradeoffs.Those having skill in the art will appreciate that there are variousvehicles by which processes and/or systems and/or other technologiesdescribed herein can be effected (e.g., hardware, software, and/orfirmware), and that the preferred vehicle will vary with the context inwhich the processes and/or systems and/or other technologies aredeployed. For example, if an implementer determines that speed andaccuracy are paramount, the implementer may opt for a mainly hardwareand/or firmware vehicle; alternatively, if flexibility is paramount, theimplementer may opt for a mainly software implementation; or, yet againalternatively, the implementer may opt for some combination of hardware,software, and/or firmware. Hence, there are several possible vehicles bywhich the processes and/or devices and/or other technologies describedherein may be effected, none of which is inherently superior to theother in that any vehicle to be utilized is a choice dependent upon thecontext in which the vehicle will be deployed and the specific concerns(e.g., speed, flexibility, or predictability) of the implementer, any ofwhich may vary. Those skilled in the art will recognize that opticalaspects of implementations will typically employ optically-orientedhardware, software, and or firmware.

The foregoing detailed description has set forth various embodiments ofthe devices and/or processes via the use of block diagrams, flowcharts,and/or examples. Insofar as such block diagrams, flowcharts, and/orexamples contain one or more functions and/or operations, it will beunderstood by those within the art that each function and/or operationwithin such block diagrams, flowcharts, or examples can be implemented,individually and/or collectively, by a wide range of hardware, software,firmware, or virtually any combination thereof. In one embodiment,several portions of the subject matter described herein may beimplemented via Application Specific Integrated Circuits (ASICs), FieldProgrammable Gate Arrays (FPGAs), digital signal processors (DSPs), orother integrated formats. However, those skilled in the art willrecognize that some aspects of the embodiments disclosed herein, inwhole or in part, can be equivalently implemented in integratedcircuits, as one or more computer programs running on one or morecomputers (e.g., as one or more programs running on one or more computersystems), as one or more programs running on one or more processors(e.g., as one or more programs running on one or more microprocessors),as firmware, or as virtually any combination thereof, and that designingthe circuitry and/or writing the code for the software and or firmwarewould be well within the skill of one of skill in the art in light ofthis disclosure. In addition, those skilled in the art will appreciatethat the mechanisms of the subject matter described herein are capableof being distributed as a program product in a variety of forms, andthat an illustrative embodiment of the subject matter described hereinapplies regardless of the particular type of signal bearing medium usedto actually carry out the distribution. Examples of a signal bearingmedium include, but are not limited to, the following: a recordable typemedium such as a floppy disk, a hard disk drive, a Compact Disc (CD), aDigital Video Disk (DVD), a digital tape, a computer memory, etc.; and atransmission type medium such as a digital and/or an analogcommunication medium (e.g., a fiber optic cable, a waveguide, a wiredcommunications link, a wireless communication link, etc.).

In a general sense, those skilled in the art will recognize that thevarious aspects described herein which can be implemented, individuallyand/or collectively, by a wide range of hardware, software, firmware, orany combination thereof can be viewed as being composed of various typesof “electrical circuitry.” Consequently, as used herein “electricalcircuitry” includes, but is not limited to, electrical circuitry havingat least one discrete electrical circuit, electrical circuitry having atleast one integrated circuit, electrical circuitry having at least oneapplication specific integrated circuit, electrical circuitry forming ageneral purpose computing device configured by a computer program (e.g.,a general purpose computer configured by a computer program which atleast partially carries out processes and/or devices described herein,or a microprocessor configured by a computer program which at leastpartially carries out processes and/or devices described herein),electrical circuitry forming a memory device (e.g., forms of randomaccess memory), and/or electrical circuitry forming a communicationsdevice (e.g., a modem, communications switch, or optical-electricalequipment). Those having skill in the art will recognize that thesubject matter described herein may be implemented in an analog ordigital fashion or some combination thereof.

Those skilled in the art will recognize that it is common within the artto describe devices and/or processes in the fashion set forth herein,and thereafter use engineering practices to integrate such describeddevices and/or processes into data processing systems. That is, at leasta portion of the devices and/or processes described herein can beintegrated into a data processing system via a reasonable amount ofexperimentation. Those having skill in the art will recognize that atypical data processing system generally includes one or more of asystem unit housing, a video display device, a memory such as volatileand non-volatile memory, processors such as microprocessors and digitalsignal processors, computational entities such as operating systems,drivers, graphical user interfaces, and applications programs, one ormore interaction devices, such as a touch pad or screen, and/or controlsystems including feedback loops and control motors (e.g., feedback forsensing position and/or velocity; control motors for moving and/oradjusting components and/or quantities). A typical data processingsystem may be implemented utilizing any suitable commercially availablecomponents, such as those typically found in datacomputing/communication and/or network computing/communication systems.

The herein described subject matter sometimes illustrates differentcomponents contained within, or connected with, different othercomponents. It is to be understood that such depicted architectures aremerely exemplary, and that in fact many other architectures can beimplemented which achieve the same functionality. In a conceptual sense,any arrangement of components to achieve the same functionality iseffectively “associated” such that the desired functionality isachieved. Hence, any two components herein combined to achieve aparticular functionality can be seen as “associated with” each othersuch that the desired functionality is achieved, irrespective ofarchitectures or intermedial components. Likewise, any two components soassociated can also be viewed as being “operably connected”, or“operably coupled”, to each other to achieve the desired functionality,and any two components capable of being so associated can also be viewedas being “operably couplable”, to each other to achieve the desiredfunctionality. Specific examples of operably couplable include but arenot limited to physically mateable and/or physically interactingcomponents and/or wirelessly interactable and/or wirelessly interactingcomponents and/or logically interacting and/or logically interactablecomponents.

While particular aspects of the present subject matter described hereinhave been shown and described, it will be apparent to those skilled inthe art that, based upon the teachings herein, changes and modificationsmay be made without departing from the subject matter described hereinand its broader aspects and, therefore, the appended claims are toencompass within their scope all such changes and modifications as arewithin the true spirit and scope of the subject matter described herein.Furthermore, it is to be understood that the invention is defined by theappended claims. It will be understood by those within the art that, ingeneral, terms used herein, and especially in the appended claims (e.g.,bodies of the appended claims) are generally intended as “open” terms(e.g., the term “including” should be interpreted as “including but notlimited to,” the term “having” should be interpreted as “having atleast,” the term “includes” should be interpreted as “includes but isnot limited to,” etc.). It will be further understood by those withinthe art that if a specific number of an introduced claim recitation isintended, such an intent will be explicitly recited in the claim, and inthe absence of such recitation no such intent is present. For example,as an aid to understanding, the following appended claims may containusage of the introductory phrases “at least one” and “one or more” tointroduce claim recitations. However, the use of such phrases should notbe construed to imply that the introduction of a claim recitation by theindefinite articles “a” or “an” limits any particular claim containingsuch introduced claim recitation to inventions containing only one suchrecitation, even when the same claim includes the introductory phrases“one or more” or “at least one” and indefinite articles such as “a” or“an” (e.g., “a” and/or “an” should typically be interpreted to mean “atleast one” or “one or more”); the same holds true for the use ofdefinite articles used to introduce claim recitations. In addition, evenif a specific number of an introduced claim recitation is explicitlyrecited, those skilled in the art will recognize that such recitationshould typically be interpreted to mean at least the recited number(e.g., the bare recitation of “two recitations,” without othermodifiers, typically means at least two recitations, or two or morerecitations). Furthermore, in those instances where a conventionanalogous to “at least one of A, B, and C, etc.” is used, in generalsuch a construction is intended in the sense one having skill in the artwould understand the convention (e.g., “a system having at least one ofA, B, and C” would include but not be limited to systems that have Aalone, B alone, C alone, A and B together, A and C together, B and Ctogether, and/or A, B, and C together, etc.). In those instances where aconvention analogous to “at least one of A, B, or C, etc.” is used, ingeneral such a construction is intended in the sense one having skill inthe art would understand the convention (e.g., “a system having at leastone of A, B, or C” would include but not be limited to systems that haveA alone, B alone, C alone, A and B together, A and C together, B and Ctogether, and/or A, B, and C together, etc.). It will be furtherunderstood by those within the art that virtually any disjunctive wordand/or phrase presenting two or more alternative terms, whether in thedescription, claims, or drawings, should be understood to contemplatethe possibilities of including one of the terms, either of the terms, orboth terms. For example, the phrase “A or B” will be understood toinclude the possibilities of “A” or “B” or “A and B.”

1. A system for administering a consumable composition, the systemcomprising: means for dispensing a first dose of a consumablecomposition according to a programmed dosing schedule; means fordetecting at least one aspect of the consumable composition; and meansfor providing a user notification according to the aspect of theconsumable composition, wherein the means for providing a usernotification according to the aspect of the consumable compositionfurther comprise: means for providing a notification of a missedingestion of a dose; wherein the means for providing a notification of amissed ingestion of a dose further comprises: means for dispensing athird consumable composition characterized by an indicator color.
 2. Thesystem of claim 1, wherein the means for providing a user notificationaccording to the aspect of the consumable composition further comprises:means for providing a notification of an upcoming dose.
 3. The system ofclaim 2, wherein the means for providing a notification of an upcomingdose further comprises: means for providing a visual notification. 4.The system of claim 2, wherein the means for providing a notification ofan upcoming dose further comprises: means for vibrating a beveragecontainer.
 5. The system of claim 2, wherein the means for providing anotification of an upcoming dose further comprises: means for providingan audible notification.
 6. The system of claim 2, wherein the means forproviding a notification of an upcoming dose further comprises: meansfor transmitting a notification to a communications device.
 7. Thesystem of claim 2, wherein the means for providing a notification of anupcoming dose further comprises: means for transmitting a notificationto an e-mail system.
 8. The system of claim 2, wherein the means forproviding a notification of an upcoming dose further comprises: meansfor transmitting a notification to a text messaging system.
 9. Thesystem of claim 2, wherein the means for providing a notification of anupcoming dose further comprises: means for transmitting a notificationto a computing device.
 10. The system of claim 1, wherein the means forproviding a user notification according to the aspect of the consumablecomposition further comprises: means for providing a notification of adispensed dose.
 11. The system of claim 10, wherein the means forproviding a notification of a dispensed dose further comprises: meansfor providing a visual notification.
 12. The system of claim 10, whereinthe means for providing a notification of a dispensed dose furthercomprises: means for vibrating a beverage container.
 13. The system ofclaim 10, wherein the means for providing a notification of a dispenseddose further comprises: means for providing an audible notification. 14.The system of claim 10, wherein the means for providing a notificationof a dispensed dose further comprise: means for dispensing a thirdconsumable composition characterized by an indicator color.
 15. Thesystem of claim 14, wherein the means for dispensing a third consumablecomposition characterized by an indicator color further comprises: meansfor dispensing a second consumable composition characterized by anindicator color visible under ultraviolet light.
 16. The system of claim10, wherein the means for providing a notification of a dispensed dosefurther comprises: means for transmitting a notification to acommunications device.
 17. The system of claim 10, wherein the means forproviding a notification of a dispensed dose further comprises: meansfor transmitting a notification to an e-mail system.
 18. The system ofclaim 10, wherein the means for providing a notification of a dispenseddose further comprises: means for transmitting a notification to a textmessaging system.
 19. The system of claim 10, wherein the means forproviding a notification of a dispensed dose further comprises: meansfor transmitting a notification to a computing device.
 20. The system ofclaim 1, wherein the means for providing a notification of a missedingestion of a dose further comprises: means for providing a visualnotification.
 21. The system of claim 1, wherein the means for providinga notification of a missed ingestion of a dose further comprises: meansfor vibrating a beverage container.
 22. The system of claim 1, whereinthe means for providing a notification of a missed ingestion of a dosefurther comprises: means for providing an audible notification.
 23. Thesystem of claim 1, wherein the means for dispensing a second consumablecomposition characterized by an indicator color further comprises: meansfor dispensing a second consumable composition characterized by anindicator color visible under ultraviolet light.
 24. The system of claim1, wherein the means for providing a notification of a missed ingestionof a dose further comprises: means for transmitting a notification to acommunications device.
 25. The system of claim 1, wherein the means forproviding a notification of a missed ingestion of a dose furthercomprises: means for transmitting a notification to an e-mail system.26. The system of claim 1, wherein the means for providing anotification of a missed ingestion of a dose further comprises: meansfor transmitting a notification to a text messaging system.
 27. Thesystem of claim 1, wherein the means for providing a notification of amissed ingestion of a dose further comprises: means for transmitting anotification to a computing device.
 28. The system of claim 1, whereinthe means for providing a user notification according to the aspect ofthe consumable composition further comprise: means for providing anotification of a failed dispensation of a dose.
 29. The system of claim28, wherein the means for providing a notification of a faileddispensation of a dose further comprises: means for providing a visualnotification.
 30. The system of claim 28, wherein the means forproviding a notification of a failed dispensation of a dose furthercomprises: means for vibrating a beverage container.
 31. The system ofclaim 28, wherein the means for providing a notification of a faileddispensation of a dose further comprises: means for providing an audiblenotification.
 32. The system of claim 28, wherein the means forproviding a notification of a failed dispensation of a dose furthercomprises: means for dispensing a third consumable compositioncharacterized by an indicator color.
 33. The system of claim 32, whereinthe means for means for dispensing a third consumable compositioncharacterized by an indicator color further comprises: means fordispensing a third consumable composition characterized by an indicatorcolor.
 34. The system of claim 28, wherein the means for providing anotification of a failed dispensation of a dose further comprises: meansfor transmitting a notification to a communications device.
 35. Thesystem of claim 28, wherein the means for providing a notification of afailed dispensation of a dose further comprises: means for transmittinga notification to an e-mail system.
 36. The system of claim 28, whereinthe means for providing a notification of a failed dispensation of adose further comprises: means for transmitting a notification to a textmessaging system.
 37. The system of claim 28, wherein the means forproviding a notification of a failed dispensation of a dose furthercomprises: means for transmitting a notification to a computing device.